I thought to build gnome-todo package 3.19 branch.

Once tried to do that, it seems to need gtk+3.0 (>= 3.19.5), however Debian doesn't have it yet (of course, it's development branch). Then tried to build gtk+3, it needs wayland 1.90 1.9.90 that has not been in Debian yet, too. So, update local package to wayland 1.9.91, found tiny bug and sent patch, and build it (package diff was sent to maintainer - and merged), easy task.

Build again, gtk+3.0 needs "wayland-protocols" that has not been packaged in Debian, yet. Okay... (20 min work...) done! Make wayland-protocols package (not ITPed yet since who should be maintainer, under same umbrella as wayland?), not difficult.

Build newest gtk+3.0 source as 3.19.8 with cowbuilder chroot with those package (cowbuilder --login --save-after-exec --inputfile foo.deb --inputfile bar.deb), ...and failed with testsuite ;) I don't have enough knowledge to investigate it.

Back to older gtk+3.0 source, build 3.19.1 is fine (diff), but 3.19.2 was failed to build, 3.19.3 to 3.19.8 were failed with testsuite.


Time is up, "You lose!"... that's one of typical days.

Many users use ftp.CC.debian.org as repository. Its name uses "ftp" for historical reason, but there's no reason to do so forever.

I've investigated some packages to check a bit, patched to it and rebuilt package. However, lintian prevent me to generate it since it has lintian error.

E: xxxx: maintainer-script-should-not-use-adduser-system-without-home postinst:23 'adduser --system --quiet --ingroup xxxx --no-create-home xxxx'

Lucas's good article: DEBIAN PACKAGES WITH /OUTDATED/ PACKAGING STYLE

Okay, then what's next? Action.

How about do "grooming" for those packages with contributors? Well experienced DDs become mentors and help to make those packages modern and put it to repo.


Packages become simple and modern, contributors can get packaging experience.
Isn't it a good idea? (Meow!)

We have regular Debian meeting at Tokyo and Kansai area (mostly Osaka).

Last month at Shibuya ( ), Norimitsu Sugimoto ( @dictoss) had a talk about Debian GNU/kFreeBSD. He's using kFreeBSD for several years, and talk with his experience was interesting. Then, I thought I can do something for kFreeBSD port, and made a patch for adding jail support with jls and jexec.

And the patch was accepted, yeah :-)

After reboot, suddenly my laptop cannot boot :-(
Then, tried to login rescue mode but root account is disabled.

Then, use USBstick to boot Ubuntu and mount encrypted volume, make root enabled.

After checking syslog, libvirt calls dmidecode and it seems that something is wrong with it.

Removed gnome-boxes and libvirt*, reboot my system and I can see login dialog by gdm3.

However, after login, I tried to exec dmidecode but nothing happened.

Also installing gnome-boxes and libvirt* packages and reboot is okay.

Okay, back to nomal. But....hmmm...? Who stole my time??

$ dpkg -s liblzma5
Package: liblzma5
Status: install ok installed
(snip)
Version: 5.1.1alpha+20120614-2.1

$ time sudo cowbuilder --build fonts-horai-umefont_530-1.dsc
real 1m8.378s
user 1m0.084s
sys 0m3.244s

real 1m9.842s
user 1m0.964s
sys 0m3.856s

real 1m9.355s
user 1m0.824s
sys 0m3.380s

xz 5.2 supports multithread, with local build (remove --disable-thread option in debian/rules)

$ dpkg -s liblzma5
Package: liblzma5
Status: install ok installed
(snip)
Version: 5.2.1-0.1

real 1m7.946s
user 0m59.628s
sys 0m3.228s

real 1m8.794s
user 1m0.072s
sys 0m3.556s

real 1m7.580s
user 0m59.152s
sys 0m3.368s

Umm, not affected.

$ time xz -T 0 fonts-horai-umefont_530.orig.tar
real 0m15.488s
user 0m47.044s
sys 0m0.252s

$ time xz -T 1 fonts-horai-umefont_530.orig.tar
real 0m40.988s
user 0m40.804s
sys 0m0.124s

multithread itself is enabled.

We've noted some instructions to release note, but probably next step is providing upgrade tool like do-release-upgrade (ubuntu) and fedup (fedora). I hope such cool tool would be provided before Stretch release.

Now I've just finished to translate Debian Jessie release note for Japanese... *Phew*

Now we're (hopefully) in the last stage for Debian "Jessie" release cycle. Well, however, "Please add your package information to release notes ASAP" style doesn't work well, IMHO.

Some package maintainer (including me ;) are lazy, they forget about changes in their package when it was pushed to a repo (put & forget about it). And "last spurt" edit is hard for translators. We translators want to finish it with Debian release time but it's really hard thing.

How wonderful if release notes would be automatically generated! So, system should help them us. Then, how about adding [releasenote] section to debian/NEWS?

In debian/changelog,

foobar (0.2.0-1) unstable; urgency=medium

* update debian/NEWS file

-- Hideki Yamane <henrich@debian.org> Wed, 20 Aug 2014 07:12:51 +0900

and debian/NEWS file,

foobar (0.2.0-1) unstable; urgency=medium

[releasenote: Stretch]
* "buz" package user should migrate other packages since this package
doesn't provide buz package anymore.

-- Hideki Yamane <henrich@debian.org> Wed, 20 Aug 2014 07:12:51 +0900

Then, parse all debian/NEWS files and generate release notes automatically.

It's just an idea, not well considered. But probably you'll get the point. "Big Bang release" style is not good, CI style is better - don't you think so?

Summary: xdg user directory spec is broken, I want to fix it.

One of annoyed things in Linux Desktop environment is localized user's directory (e.g. $HOME/ , instead of $HOME/Download). I know it is handled by XDG, my ~/.config/user-dirs.dirs has setting as below (by default).

XDG_DESKTOP_DIR="$HOME/ "
XDG_DOWNLOAD_DIR="$HOME/ "
XDG_TEMPLATES_DIR="$HOME/ "
XDG_PUBLICSHARE_DIR="$HOME/ "
XDG_DOCUMENTS_DIR="$HOME/ "
XDG_MUSIC_DIR="$HOME/ "
XDG_PICTURES_DIR="$HOME/ "
XDG_VIDEOS_DIR="$HOME/ "

So XDG utlility program changes it as setting, moves ~/Desktop to ~/ . However, it is NOT what users want.

Because if you would play with shell, you should also input localized characters in your terminal. Imagine, sometimes I download files with browser, then use it in terminal - download some tar.xz file and extract it. Well, it is downloaded in ~/ directory... it's not convinient - you cannot use tab completion without IME (input method editor), e.g. Anthy or Mozc for Japanese. And if you don't want to install it, what do you do? Use mouse to copy&paste?

Then, some Japanese people create webpages about "How to change localized user directory back to English name" ;)

Windows and OS X has localized Desktop, Download, Document directory, too. But it's not directory itself. In Windows, you can see " " (Desktop) with Windows Explorer but it is seen as just "Desktop" directory with cmd.exe (I don't know how to trick it. Maybe Windows registory magic). And in OS X, same thing with Finder. Those users don't annoy with localized directory name, it's friendly and convinient for cmd/shell users, and also for GUI (Windows' Explorer/OS X's Finder) users.


And also, it seems that localized directory name is good for average users who use File manager (Nautilus, etc). Just labeled with only English is not friendly to non-English native users like my mother ;) (Yes, localization is important!) But it's _better_ for *everyone* to set directory name with English _and_ localized with hardlink (and probably not harm anyone).

So lazyweb, could you tell me where should I go to talk this issue with upstream? It's not big thing, but still annoying. I can change it with xdg-user-dirs-update for my environment but it's just a workaround, not solution for this problem.